Error on Open a Module

Hi Users,

I dono what went wrong. I get the errors below when I click on a module and open it. Module not getting open.

Some clues may help. I uninstalled ( license keys, installation manager, doors client and database server) and reinstalled but no luck.

I tried this as well http://www-01.ibm.com/support/docview.wss?uid=swg21621656 but no clue what i'm missing.

I'm using Doors V9.6.1.0 in windows 7 machine everything was working good. Dono what happened in between

Someone please assist to solve this issue

Thanks in advance

 

 

DXL Interaction WIndow:
 
-R-E- DXL: <config/baseWindowCallbacks. inc:1737> An unexpected error has occurred: doors.exe caused an EXCEPTION_ACCESS_VIOLATION in module doors.exe at 0000000040597EE3
 
Backtrace:
<config/baseWindowCallbacks. inc:1827> 
-R-F- DXL: <config/baseWindowCallbacks. inc:1737> internal error, please submit a bug report
Backtrace:
<config/baseWindowCallbacks. inc:1827> 

 

Diagnostic Log:
 
DOORS: **** Translating a structured exception ****
DOORS: Version 9.6.1.0, build number 96113, built on Nov 13 2014 21:28:31.
DOORS: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
DOORS: DOORS: 71 percent of memory is in use.
DOORS: There are 6172808 total Kbytes of physical memory.
DOORS: There are 1734828 free Kbytes of physical memory.
DOORS: There are 12343780 total Kbytes of paging file.
DOORS: There are 6368540 free Kbytes of paging file.
DOORS: There are ffffff80 total Kbytes of virtual memory.
DOORS: There are fff90b78 free Kbytes of virtual memory.
 
DOORS: argv[0]: C:\Program Files\IBM\Rational\DOORS\9.6\ bin\doors.exe
DOORS: Exception timestamp: 01/02/2016 at 20:04:20
DOORS: doors.exe caused an EXCEPTION_ACCESS_VIOLATION in module doors.exe at 0000000040597EE3
DOORS: 0x00000140597ee3 doors.exe
0x000001405981f6 doors.exe
0x0000014064f0b5 doors.exe
0x00000140655e05 doors.exe
0x00000141e3a4b4 doors.exe
0x000001400e20fe doors.exe
0x000001400e8786 doors.exe
0x00000140e9571f doors.exe
0x00000140e9da9d doors.exe
0x000001407f5e05 doors.exe
0x000001407f85c7 doors.exe
0x000001407f72e1 doors.exe
0x000001408dd47b doors.exe
0x000001407f5b25 doors.exe
0x000001407f72e1 doors.exe
0x000001407f6e57 doors.exe
0x000001407f730b doors.exe
0x000001407f730b doors.exe
0x000001407f72e1 doors.exe
0x000001407f730b doors.exe
0x000001407f730b doors.exe
0x000001407ce3b3 doors.exe
0x000001407c1b9d doors.exe
0x000001405a6555 doors.exe
0x0000014058190d doors.exe
0x0000014055e9a9 doors.exe
0x00000076d69c11 USER32.dll, TranslateMessageEx()+00000669 byte(s)
0x00000076d66ab8 USER32.dll, SetTimer()+00000376 byte(s)
0x00000076d66bbd USER32.dll, SendMessageW()+00000093 byte(s)
0x0007fefb6c9845 COMCTL32.dll, Ordinal342()+00004817 byte(s)
0x0007fefb7c60b9 COMCTL32.dll, TaskDialog()+00751001 byte(s)
0x0007fefb726aec COMCTL32.dll, TaskDialog()+00098252 byte(s)
0x0007fefb7260c5 COMCTL32.dll, TaskDialog()+00095653 byte(s)
0x00000076d69c11 USER32.dll, TranslateMessageEx()+00000669 byte(s)
0x00000076d63bd4 USER32.dll, CallWindowProcW()+00000156 byte(s)
0x00000076d63b50 USER32.dll, CallWindowProcW()+00000024 byte(s)
0x00000140584a50 doors.exe
0x0000014057c6e0 doors.exe
0x000001405a790a doors.exe
0x00000076d69c11 USER32.dll, TranslateMessageEx()+00000669 byte(s)
0x00000076d63bd4 USER32.dll, CallWindowProcW()+00000156 byte(s)
0x00000076d63b50 USER32.dll, CallWindowProcW()+00000024 byte(s)
0x0007fefb6c6205 COMCTL32.dll, CreateUpDownControl()+00009549 byte(s)
0x0007fefb6c6990 COMCTL32.dll, DefSubclassProc()+00000692 byte(s)
0x0007fefb6c6758 COMCTL32.dll, DefSubclassProc()+00000124 byte(s)
0x0007fefb6c6990 COMCTL32.dll, DefSubclassProc()+00000692 byte(s)
0x0007fefb6c6867 COMCTL32.dll, DefSubclassProc()+00000395 byte(s)
0x00000076d69c11 USER32.dll, TranslateMessageEx()+00000669 byte(s)
0x00000076d6992a USER32.dll, TranslateMessage()+00000490 byte(s)
0x00000140565d4e doors.exe
0x0000014053f99f doors.exe
0x0000014001cbd7 doors.exe
0x0000014001dd9c doors.exe
0x00000076c459ed kernel32.dll, BaseThreadInitThunk()+00000013 byte(s)
0x00000076e7b831 ntdll.dll, RtlUserThreadStart()+00000033 byte(s)
 
DOORS: **** end of event ****
DOORS: Writing exception details...
DOORS: Exception details have been written to: C:\Users\admin\AppData\Local\ Temp\DOORS-96113-2016_02_01- 20_04_20-5816-5352.dmp
DOORS: **** Translating a structured exception ****
DOORS: Version 9.6.1.0, build number 96113, built on Nov 13 2014 21:28:31.
DOORS: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
DOORS: DOORS: 72 percent of memory is in use.
DOORS: There are 6172808 total Kbytes of physical memory.
DOORS: There are 1728336 free Kbytes of physical memory.
DOORS: There are 12343780 total Kbytes of paging file.
DOORS: There are 6360948 free Kbytes of paging file.
DOORS: There are ffffff80 total Kbytes of virtual memory.
DOORS: There are fff8dcb4 free Kbytes of virtual memory.
 
DOORS: argv[0]: C:\Program Files\IBM\Rational\DOORS\9.6\ bin\doors.exe
DOORS: Exception timestamp: 01/02/2016 at 20:04:20
DOORS: doors.exe caused an EXCEPTION_ACCESS_VIOLATION in module doors.exe at 0000000040597EE3
DOORS: 0x00000140597ee3 doors.exe
0x000001405981f6 doors.exe
0x0000014064f0b5 doors.exe
0x00000140655e05 doors.exe
0x00000141e3a4b4 doors.exe
0x000001400e20fe doors.exe
0x000001400e8786 doors.exe
0x00000140e9571f doors.exe
0x00000140e9da9d doors.exe
0x000001407f5e05 doors.exe
0x000001407f85c7 doors.exe
0x000001407f72e1 doors.exe
0x000001408dd47b doors.exe
0x000001407f5b25 doors.exe
0x000001407f72e1 doors.exe
0x000001407f6e57 doors.exe
0x000001407f730b doors.exe
0x000001407f730b doors.exe
0x000001407f72e1 doors.exe
0x000001407f730b doors.exe
0x000001407f730b doors.exe
0x000001407ce3b3 doors.exe
0x000001407c1b9d doors.exe
0x000001405a6555 doors.exe
0x0000014058190d doors.exe
0x0000014055e9a9 doors.exe
0x00000076d69c11 USER32.dll, TranslateMessageEx()+00000669 byte(s)
0x00000076d66ab8 USER32.dll, SetTimer()+00000376 byte(s)
0x00000076d66bbd USER32.dll, SendMessageW()+00000093 byte(s)
0x0007fefb6c9845 COMCTL32.dll, Ordinal342()+00004817 byte(s)
0x0007fefb7c60b9 COMCTL32.dll, TaskDialog()+00751001 byte(s)
0x0007fefb726aec COMCTL32.dll, TaskDialog()+00098252 byte(s)
0x0007fefb7260c5 COMCTL32.dll, TaskDialog()+00095653 byte(s)
0x00000076d69c11 USER32.dll, TranslateMessageEx()+00000669 byte(s)
0x00000076d63bd4 USER32.dll, CallWindowProcW()+00000156 byte(s)
0x00000076d63b50 USER32.dll, CallWindowProcW()+00000024 byte(s)
0x00000140584a50 doors.exe
0x0000014057c6e0 doors.exe
0x000001405a790a doors.exe
0x00000076d69c11 USER32.dll, TranslateMessageEx()+00000669 byte(s)
0x00000076d63bd4 USER32.dll, CallWindowProcW()+00000156 byte(s)
0x00000076d63b50 USER32.dll, CallWindowProcW()+00000024 byte(s)
0x0007fefb6c6205 COMCTL32.dll, CreateUpDownControl()+00009549 byte(s)
0x0007fefb6c6990 COMCTL32.dll, DefSubclassProc()+00000692 byte(s)
0x0007fefb6c6758 COMCTL32.dll, DefSubclassProc()+00000124 byte(s)
0x0007fefb6c6990 COMCTL32.dll, DefSubclassProc()+00000692 byte(s)
0x0007fefb6c6867 COMCTL32.dll, DefSubclassProc()+00000395 byte(s)
0x00000076d69c11 USER32.dll, TranslateMessageEx()+00000669 byte(s)
0x00000076d6992a USER32.dll, TranslateMessage()+00000490 byte(s)
0x00000140565d4e doors.exe
0x0000014053f99f doors.exe
0x0000014001cbd7 doors.exe
0x0000014001dd9c doors.exe
0x00000076c459ed kernel32.dll, BaseThreadInitThunk()+00000013 byte(s)
0x00000076e7b831 ntdll.dll, RtlUserThreadStart()+00000033 byte(s)
 
DOORS: **** end of event ****
DOORS: Writing exception details...
DOORS: Exception details have been written to: C:\Users\admin\AppData\Local\ Temp\DOORS-96113-2016_02_01- 20_04_20-5816-5352.dmp
 
BR

Nabil


maknabil - Mon Feb 01 09:52:06 EST 2016

Re: Error on Open a Module
Mathias Mamsch - Tue Feb 02 02:07:33 EST 2016

Hmm ... not much to see from your traceback. I see "0x00000076d66ab8 USER32.dll, SetTimer()+00000376 byte(s)" which could hint to a bad DXL script. 

Is this only happening with one module? Or with all modules you click on?

Regards, Mathias

Re: Error on Open a Module
Mathias Mamsch - Tue Feb 02 02:09:20 EST 2016

Mathias Mamsch - Tue Feb 02 02:07:33 EST 2016

Hmm ... not much to see from your traceback. I see "0x00000076d66ab8 USER32.dll, SetTimer()+00000376 byte(s)" which could hint to a bad DXL script. 

Is this only happening with one module? Or with all modules you click on?

Regards, Mathias

Please also browse the forum for "database triggers remove" ... See if someone might have installed a trigger, that crashes DOORS when opening a module. 

Regards, Mathias